home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
qbbs
/
otbank20.zip
/
OTBANK.DOC
< prev
next >
Wrap
Text File
|
1991-01-18
|
10KB
|
225 lines
╒═════════════════════════════════════════════════════════════════════════╕
│░░░░░░ On-line Time Bank ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘═════════════════════════════════════════════════════════════════════════╛
On-line Time Bank for @QBBS/RA/@SBBS
Version 2.0
By: William L. Munson
This is another fine utility from:
The Munchkin's Node BBS
(716) 872 - 2338
300 - 2400 baud on-line 24 hours/day
Fido Net/Node 1:260/238
╒═════════════════════════════════════════════════════════════════════════╕
│░░░░░░ INTRODUCTION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘═════════════════════════════════════════════════════════════════════════╛
Would you like to be able to allow your users to save their unused
on-line time for use at a later date? Have you been afraid that the
user would be able to over-run your system events or tie up your
system for several hours during your peak usage times? Well have I
got a nice surprise for you!!. Enter the On-line Time Bank. This
banking program will allow your users to save their extra time into a
bank account whenever they wish. It will also allow them to withdraw
as needed but with some restrictions. They will not be allowed to
withdraw enough time to over-run your system events as defined in your
@config file. Also you may set the program up so that the users cannot
withdraw more than a set limit during a sysop definable time period
thus ensuring that your board is available to your users during your
peak usage times. Users may also take out a 'loan' of time which they
are forced to pay back via direct daily deductions from their on-line
time. Also as an added bonus, your users may purchase lotto tickets
with their deposited time. The lotto can let the lucky user win up to
80 times their bet. Both the loan feature and the time lotto my be
disabled by the sysop.
╒═════════════════════════════════════════════════════════════════════════╕
│░░░░░░ INSTALLATION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘═════════════════════════════════════════════════════════════════════════╛
OTBANK may be installed in a directory of it's own or in the same
directory as your BBS files. The files OTBANK.@EXE and OTBANK.@CFG
should be placed in the same directory and @OTBMAINT.EXE must be placed
in the same directory as your system's USERS.BBS file. Next, edit
OTBANK.CFG to configure the program the way you like. The
configuration file is described below. If you wish to have automatic
'direct deposit' type payments on your users outstanding loans then
install OTBMAINT.EXE as part of your nightly maintenance batch. See the
docs for the program for the details on the setup of the OTBMAINT.EXE.
╒═════════════════════════════════════════════════════════════════════════╕
│░░░░░░ CONFIGURATION FILE ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘═════════════════════════════════════════════════════════════════════════╛
You may edit the configuration file with any text editor which
will create a plain ASCII text file. The format of the configuration
commands is as follows.
COMMAND = COMMAND'S VALUE
Any line which is not a command must begin with a semi-colon and is
considered to be a comment. You may enter as many comments as you wish.
I have included a sample configuration file for you to edit. Here is a
short description of the function of each command.
@REG_NUMBER = 0
This is where you put the registration code which I will send you when
you send in the registration fee of $10.00.
BANK_NAME =
Set this to whatever name you would like to give to your bank. This is
NOT the same as the BBS name you send with your registration.
BANK_MANAGER =
Set this to the name of the person who "manages" the bank. This may be
whatever you would like and does not need to be a real person.
INHIBITED_START =
This is the start time in 24 hour format when users will not be able
to take unlimited ( except by system event. ) time from their bank
account. During the inhibited period a user will only be able to take
out time until their total on-line time for the entire day would equal
the limit set by INHIBITED_LIMIT. Set this to 0000 to disable the
inhibit feature entirely. ( Also see INHIBIT_STOP and INHIBIT_LIMIT.)
INHIBITED_STOP =
This is the time in 24 hour format when the withdraw limits are
removed. If this time is set to an earlier time than the start time
then the door will assume that the inhibit hours include midnight.
Also set this to 0000 to disable the inhibit feature completely.
INHIBITED_LIMIT =
This is the maximum amount of time which a user can have available for
use during the inhibited hours. If set to a number lower than the
user's normal daily time limit then the user will not be able to take
time out of the bank during the inhibited hours. Set this to zero to
disable the inhibit feature completely.
LOAN_LIMIT =
This is the maximum amount of time a user can take out in a loan. The
loaned time is deposited in the user's account so that any restrictions
on withdrawals will be enforced.
LOAN_INTEREST =
This is the amount of time ( as a percentage of the total loan ) which
is tacked onto the amount of the loan as interest.
LOAN_PAYMENT =
This is the amount of time that OTBMAINT.EXE will withdraw from a
user's on-line time as part of your nightly maintenance event until the
loan is paid off. This will only work if you run OTBMAINT.EXE as part
of your event.
ACCOUNT_MAXIMUM =
This is the maximum amount of time a user can deposit into their
bank account. A person may exceed this value by taking out a loan
but will not be able to manually deposit anything else until their
balance falls below the maximum limit.
ALLOW_GAMBLING =
This is a YES/NO answer. If set to NO then the gambling option will
not be displayed to the user and they will not be able to select it.
ALLOW_LOANS =
This is a YES/NO answer. If set to no then the loan option will not
be displayed and the user will not be able to select it.
This completes the configuration of the program.
╒═════════════════════════════════════════════════════════════════════════╕
│░░░░░░ OPERATION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘═════════════════════════════════════════════════════════════════════════╛
The program may be run as either a type 7 or type 15 exit. The door
needs a command line in order to run. The format of the command line
is as follows:
OTBANK [Path to BBS files] [Path to bank files]
The BBS files path points to the directory where the BBS writes the
EXITINFO.BBS and DORINFOx.DEF files for that node.
The bank files path points to where you want to keep your bank account
and config files.
Here is an excerpt of the batch file to call the program as a type 15
exit.
REM RUN OTBANK
CD \
CD \BANK
OTBANK c:\ra\ c:\ra\otbank\
CD \
CD \RA
RA -R -E0
@GOTO RESTART
Here is an example of the batch file to call the program as a type 7
exit.
@ECHO OFF
CD \
CD \BANK
OTBANK C:\RA\ c:\ra\otbank\
CD \
CD \RA
OTBANK monitors the status of the carrier and will return to the BBS
if carrier is lost. There is also a time out timer to return control
to the bbs after about 5 minutes of in-activity.
For your convenience, I have included a pre-printed registration form.
The form is included in a file named OTBANK.REG which is part of this
archive.
╒═════════════════════════════════════════════════════════════════════════╕
│░░░░░░ REGISTRATION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘═════════════════════════════════════════════════════════════════════════╛
OTBANK is a shareware product! This means that if you decide to use
this program on a regular basis you should register it. Registration
is only $10.00 so you really don't have any excuse for not doing it.
What do you get for your registration? You get a program which is
personalized with your BBS system's name instead of with the
un-registered program notice. You also get a good feeling from knowing
that you have supported one of the best software marketing methods
available.
If I get enough people registering this program I will continue to
write updates of this and the other fine products which I have
written.
I have written another companion program for this bank door. It is
for those sysops who use the fine program FileDoor. The name of my
program is FileDoor Helper and allows you to control your users
downloading access by monitoring the ratio of uploads to downloads.
It will set or reset a sysop defined flag when a violation occurs. It
also allows for direct crediting of the bank account maintained by
this program or direct crediting of the users on-line time. There are
many other nice features which I will not define here. The file name
of the current version of FileDoor Helper is: RA-@FDH12.ZIP and should
be available where you found this program.